Systems and methods for completing transactions via curbside service

ABSTRACT

A method performed by a processor of a financial institution computing system includes receiving a curbside transaction description from a user device, transmitting a curbside set-up request to a branch location computing system associated with the branch location, transmitting curbside transaction information to the user device, receiving location information from the user device indicative of the user device being located at the branch location, receiving an authentication identifier from the user device, wherein receiving the authentication identifier initiates the curbside transaction, and servicing the account holder via a receptacle of a plurality of receptacles, the receptacle chosen based on the location information and the curbside transaction description.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. Non-Provisional applicationSer. No. 16/199,052 entitled “SYSTEMS AND METHODS FOR COMPLETINGTRANSACTIONS VIA CURBSIDE SERVICE,” filed Nov. 23, 2018, which is acontinuation of U.S. Non-Provisional application Ser. No. 15/477,309entitled “SYSTEMS AND METHODS FOR COMPLETING TRANSACTIONS VIA CURBSIDESERVICE”, filed Apr. 3, 2017, which claims the benefit of U.S.Provisional Patent Application No. 62/321,576 entitled “SYSTEMS ANDMETHODS FOR COMPLETING TRANSACTIONS VIA CURBSIDE SERVICE”, filed Apr.12, 2016, all of which are incorporated herein by reference in theirentirety.

BACKGROUND

Financial institutions provide a plethora of financial services tocustomers to assist in the completion of transactions and to meet theneeds of the customers. One service includes assisting with transactionsthat involve “in-hand” funds, for example, the withdrawal or deposit ofcash. Currently, a customer may engage in the withdrawal and deposit ofthese funds by walking into a branch location of a financial institutionand initiating the withdrawal or deposit request via interaction with ateller at the branch. At some branch locations, the customer can stay ina vehicle and enter an attached drive-through to initiate the withdrawalor deposit request via interaction with a teller at the branch over atelecom. However, the customer is only able to access the financialinstitution during operating hours, which are usually between the hoursof 9 AM to 5 PM. Many customers may find these hours inconvenient and inconflict with their work schedules, requiring them to leave a job duringthe work day to complete the desired transaction. While a financialinstitution may have automated teller machines (ATMs) in variouslocations outside of a branch location to allow the customer, at anyhour of the day, to withdraw cash after authenticating at the ATM, thetype of transactions may be limited to just withdraws and deposits.Despite the ability to engage in these “in-hand” fund transactionsinside branch locations and at ATMs, there is a need for more flexiblesystems and methods to engage in these transactions, more convenience,and a more time effective method to complete these transactions.

SUMMARY

Various embodiments relate to a method performed by a financialinstitution computing system. One example method includes receiving acurbside transaction request to execute a transaction from a user deviceof an account holder of the financial institution. The curbsidetransaction request includes at least one of a transaction descriptionand a transaction time. The financial institution determines a branchlocation from a plurality of branch locations associated with thefinancial institution for which to carry out the transaction. Thefinancial institution transmits a curbside set-up request to the branchlocation. The financial institution also transmits the curbsidetransaction information to the user device. The curbside transactioninformation sent to the user device includes the branch location andauthentication details.

Various other embodiments relate to a method performed by a financialinstitution's branch computing system that is associated with afinancial institution. One example method includes receiving, from afinancial institution computing system, a curbside set-up request. The acurbside set-up request includes at least one of a transactiondescription and a transaction time. The branch computing systemgenerates an employee instruction based on the curbside set-up request.The branch receives an arrival notification, the arrival notification isresponsive to an account holder arriving at the branch location to beginthe curbside transaction. Upon completion of the transaction, the branchgenerates a transaction completion message based on a transaction offunds at the branch location.

Various other embodiments relate to a financial institution computingsystem associated with a financial institution. One example systemincludes a network interface configured to communicate data to and froma branch computing system associated with a branch of the financialinstitution and a user device associated with a user over a network. Thesystem also includes a branch database that contains informationrelating to the curbside service availability of the financialinstitution branches associated with the financial institution. Thefinancial institution has a circuit structured to execute a series ofcommands. The series of commands include receiving a curbsidetransaction request from a user device that is associated with anaccount holder of the financial institution. The curbside transactionrequest includes at least one of a transaction description and atransaction time. The series of commands include determining a branchlocation from a plurality of branch locations associated with thefinancial institution. The determination is based, in part, on thetransaction description and transaction time. The series of commandsinclude transmitting a curbside set-up request to the branch computingsystem and transmitting the curbside transaction information to the userdevice.

These and other features, together with the organization and manner ofoperation thereof, will become apparent from the following detaileddescription when taken in conjunction with the accompanying drawings,wherein like elements have like numerals throughout the several drawingsdescribed below.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 is a schematic diagram of a curbside transaction processingsystem, according to an example embodiment.

FIG. 2 is a flow diagram of a method of transmitting a curbsidetransaction request, according to an example embodiment.

FIG. 3 is a flow diagram of a method of completing a curbsidetransaction request, according to an example embodiment.

FIGS. 4A-4D illustrate display screens that may be displayed the userduring the methods of FIG. 2 and FIG. 3.

DETAILED DESCRIPTION

Referring generally to the figures, systems and methods for completingbanking transactions (e.g., withdrawing, depositing and exchangingcurrency) via a curbside service are described. The embodimentsdescribed herein alleviate the time uncertainty and inconvenienceassociated with conducting transactions involving the physical passingof items (e.g., coins and bills) that are limited to a financialinstitution. For example, various embodiments reduce the uncertainty ofwait time and organize the transaction before the account holder arrivesat the financial institution's branch to complete the transaction. Thedescribed systems and methods enable account holders to easily engage inwithdrawals, deposits, currency exchanges, and the like, in accordancewith the account holder's terms, time and schedule, all without theaccount holder having to leave the comfort of the vehicle.

As described in further detail below, the account holder interacts withthe financial institution, at the leisure of the account holder, tosubmit a request to complete a transaction curbside at one of thefinancial institution's branch locations. The embodiments account holderselects from a variety of options including a transaction type, atransaction amount, a transaction location, and a transaction time. Theoptions allow the account holder to structure a transaction that fitsthe account holder's needs and time constraints. For example, theaccount holder can interact with the financial institution via afinancial institution application or website in real-time to receiveopen curbside transaction times and locations for all of the financialinstitution branches that offer the curbside service. On the backend,the financial institution works with the available branches to providethe account holder with the available time slots and locations tocomplete the account holder's requested transactions. Once a request issubmitted, the financial institution's branch organizes the transactionitems to complete the transaction when the account holder arrives. Theaccount holder can submit the request on any web-enabled device, forexample a desktop, laptop, cellphone, or other mobile computing devices.The transaction request may relate to any combination of a deposit offunds, a withdrawal of funds, an exchange of a first type of funds for asecond type of funds (e.g., a foreign exchange transaction, an exchangeof bills for coins, an exchange of coins for bills, etc.), or the like.Once the request is submitted, the financial institution identifies asuitable branch location for the transaction, informs the account holderof the branch location and the transaction window time, and configuresthe financial institution's branch for completion of the transaction(e.g., by preparing physical funds for delivery to the customer onarrival). Accordingly, the account holder will have certainty that, whenarriving at the branch location at the designated date and time, thetransaction can be completed.

FIG. 1 is a schematic diagram of a curbside transaction system 100,according to an example embodiment. The curbside transaction system 100includes one or more customer computing system(s) 102, a financialinstitution computing system 104 associated with a financial institution(e.g., a bank), and a financial institution branch computing system 106associated with an individual branch of the financial institution. Eachof the customer computing system 102, the financial institutioncomputing system 104, and the financial institution branch computingsystem 106 are in operative communication with each other via a network108. The network 108 includes, for example, the Internet, cellularnetworks, proprietary banking networks, and the like. In somearrangements, the financial institution computing system 104 and thefinancial institution branch computing system 106 are in communicationvia a secure network or intranet, such as an internal banking networkassociated with the financial institution.

Generally, customers (e.g., an account holder at the financialinstitution) use the curbside transaction system 100 to submit a requestto the financial institution computing system 104 to engage in arequested curbside transaction. Through a user interface provided by thefinancial institution (e.g., via a smartphone application, via an onlinebanking website, etc.), the customer can authenticate himself or herselfas an account holder with the financial institution, select a desiredtransaction type (e.g., withdrawal, deposit, exchange, etc.), providerelevant transaction descriptions (e.g., amount of currency, type ofcurrency, desired date and time of transaction, etc.), identify a branchlocation and a transaction time window for which the customer cancomplete the transaction in accordance with the customer's schedule(e.g., by selecting an available branch on the user interface, byaffirming a financial institution suggested available branch, etc.). Thefinancial institution computing system 104 automatically generates thetransaction message and sends it to the computing system 106 of thedetermined branch of the financial institution. The branch computingsystem 106 executes commands related to the received transactionmessage. The commands direct the branch location's employees to completethe customer's request. For example, the employee physically preparesthe relevant transaction materials in anticipation of the transactiontime.

The customer computing systems 102 include a network interface circuit112, a display 114, an input/output device 116, and a curbside bankingcircuit 118. The network interface 112 is structured to facilitateoperative communication between the customer computing systems 102 andother systems and devices over the network 108. The customer computingsystems 102 may include any of smartphones, tablet computing systems,laptop computing systems, desktop computing systems, PDAs, smartwatches, smart glasses, tablets, etc.

The display 114 is structured to present user interfaces to thecustomers. For example, when customers use the customer computingsystems 102 to access a financial institution application or website,the display 114 presents account information, transaction information,and the like, to the customers. The input/output device 116 isstructured to receive input from the customer via the customer computingsystems 102. In some arrangements, the display 114 and the input outputdevice 116 are combined (e.g., as a touchscreen display). As describedin further detail below, the input/output relates to curbsidetransaction requests, location selection, personal information, vehicleinformation and other information used to facilitate transactionsbetween the financial institution, the customers, and the financialinstitution branches that offer curbside service. The input/outputdevice 116 can be used by the customer to provide transactiondescriptions (e.g., transaction type, branch location, transactionamount in U.S.D. currency or foreign currency, transaction window, etc.)to be carried out by the financial institution computing system 104 andthe financial institution branch computing system 106. The input/outputdevice 116 may include a keyboard, a mouse, a touchscreen, a biometricsensor (e.g., a fingerprint sensor), a microphone, a camera, etc.

The curbside banking circuit 118 is structured to provide the customerwith a user interface to arrange for financial transactions with thefinancial institution via one of the branch locations. For example, viathe curbside banking circuit 118, the customer can withdraw funds,deposit funds, exchange funds or complete similar transactions at abranch location. The curbside banking circuit 118 may comprise programlogic (e.g., stored executable instructions) structured to cause aprocessor to implement at least some of the functions described herein.The curbside banking circuit 118 may be formed at least in part by webbrowser (e.g., Safari®, Chrome®, Internet Explorer®, etc.) configured toreceive and display web pages received from the financial institutioncomputing system 104. In other arrangements, the curbside bankingcircuit 118 is formed, at least in part, by a dedicated application(e.g., a smartphone application), a text message interface, or anotherprogram executed locally on the customer computing system 102 suitablefor communicating with the financial institution computing system 104over the network 108. This facilitates the customers' ability to have abranch location be prepped, and an employee or machine at the branchready to deliver the customer specified transaction to the customer'svehicle. The customer logs into his or her existing financialinstitution account by providing online banking credentials (e.g., ausername and password) via the curbside banking circuit 118 and submit acurbside transaction request, with available curbside locations andpickup window choices being responsive to the customer transaction typeand customer location. The curbside banking circuit 118 can also providethe customer with transaction descriptions including curbside location,parking spot, or any authentication information. Example interfacesgenerated by the curbside banking circuit 118 for display to thecustomer via the display 114 are shown in FIGS. 4A-D.

In some embodiments, the financial institution computing system 104provides the programming instructions necessary to implement thecurbside banking circuit 118 as part of a software application madeavailable for download and installation on the customer computingsystems 102 (e.g., via the online banking website of the bank, via anapp store, or in another manner). Responsive to a user selection of anappropriate link, the curbside banking circuit 118 for requesting acurbside transaction through the customer's deposit account, istransmitted to the customer computing system 102 from the financialinstitution computing system 104 and may cause itself to be installed onthe customer computing system 102. Installation of the softwareapplication creates the curbside banking circuit 118 on the customercomputing system 102.

The financial institution computing system 104 includes a networkinterface circuit 120, a curbside management circuit 122, an accountprocessing circuit 128, and an account database 130. The financialinstitution computing system 104 may, for example, include one or moreservers each with one or more processors configured to executeinstructions stored in a memory, send and receive data stored in thememory, and perform other operations to implement the financial servicesdescribed herein associated with the processing modules, databases, andprocesses. In some arrangements, the financial institution computingsystem 104 also includes the financial institution branch computingsystem 106.

The network interface 120 is structured to facilitate operative datacommunication between the financial institution computing system 104 andother systems and devices over the network 108 (e.g., the customercomputing systems 102, the financial institution branch computing system106, etc.) and/or over a secure network or intranet, such as an internalbanking network associated with the financial institution.

The curbside management circuit 122 is structured to facilitate thebackend processes necessary to conduct curbside transaction via thecustomer's financial account. For example, the curbside managementcircuit 122 is structured to receive transaction requests from customercomputing systems 102, generate transaction instructions based onreceived transaction requests, and send the transaction instructions tothe financial institution branch computing system 106 associated with aspecific branch location, to facilitate the requested transaction at thespecified time. The curbside management circuit 122 includes the requestcircuit 124, the curbside instructions circuit 126 and a branch database127.

The request circuit 124 is structured to receive and process a customertransaction request to engage in the curbside service. The requestcircuit 124 has access to the branch database 127. The branch database127 stores information regarding the financial institution branchlocations that offer the curbside service, the curbside transactiontypes accepted at a given branch location, the curbside serviceavailability (e.g., available days and time slots), the financialinstitution's branches various currency supplies and other informationrelated to a customer transaction request. For example, thefunctionality of the request circuit 124 is initiated in response to thefinancial institution computing system receiving a transaction requestor availability inquiry from a customer via the curbside banking circuit118 on the customer computing system 102. In some arrangements, therequest circuit 124 is in real-time communication with customer devicesuch that the interface on the device updates the information fields forthe request updates in response to the customer entries. For example, ifthe customer were to select the exchange currency option and enter thecustomer's zip code, the request circuit 124 may determine that out ofthe plurality of financial institution branch locations near thecustomer's location, only two of the locations could complete therequested transaction (e.g., based on known capabilities and limitationsof the financial institution branches, based on real-time on-handcurrency quantities of the financial institution branches, etc.). Therequest circuit 124 could limit the display of the potential financialinstitution branch locations to those two locations. In otherarrangements, the request circuit 124 could receive all the relevanttransaction request details (e.g., transaction type, branch location,transaction amount in United States dollars (“U.S.D.”) or foreigncurrency, etc.) and then make the determination of feasibility. Forexample, the request circuit 124 could receive a transaction request fora withdrawal of 20 U.S.D., between 3:00 PM and 3:10 PM, at the financialinstitution branch location on ABC Drive. The request circuit 124 coulddetermine that the branch location could handle that transaction and therequest circuit 124 could approve that transaction, prompting thecurbside instructions circuit 126 to generate the financial institutionbranch location instructions that are transmitted to the financialinstitution branch computing system 106. Alternatively, the requestcircuit 124 could determine that the requested branch location would notbe able to comply with the customer request, and the request circuit 124could deny the request or provide to the requesting customer alternativebranch locations or times that could complete the transaction.

Upon approval of a request by the request circuit 124, the curbsideinstructions circuit 126 is structured to generate and transmit thetransaction instructions (e.g., transaction type, passcode information,vehicle information, customer picture, transaction amount in U.S.D.currency or foreign currency, etc.) to the proper financial institutionbranch computing system 106 associated with the user-identified orselected financial institution branch location. The curbsideinstructions circuit 126 can also assign a specific parking spotlocation for the customer to arrive in. For example, the request circuit124 can compile and provide the finalized request information to thecurbside instructions circuit 126 which in turn assigns a parking spot Aat the financial institution's branch location for the transaction tooccur at. Additionally, the curbside instructions circuit 126 organizesthe authentication information for the transaction request. The curbsideinstructions circuit 126 generates authentication details for thetransaction, for example, transmitting customer pickup vehicleinformation, a photo of the customer, or a passcode to use when arrivingat the parking spot. In some arrangements, the curbside instructionscircuit 126 is structured to transmit the finalized transactiondescriptions, including the curbside number and passcode information, tothe customer computing system 102. For example, the curbsideinstructions circuit 126 transmits that the customer arrive at thebranch located on “123 Street” and park in spot A between the hours of3:00 PM and 3:15 PM, bringing with them one form of identification and afinancial institution generated email containing a verbal passcode.

The account processing circuit 128 is structured to track, maintain, andincorporate transaction descriptions for an account enrolled in thecurbside transaction service with the financial institution. The accountprocessing circuit 128 interacts with the curbside management circuit122 and the curbside completion circuit 142 of the financial institutionbranch computing system 106, to properly adjust the customer's financialaccount. In some arrangements, the account processing circuit 128temporarily debits or credits the customer's financial account when thecurbside management circuit 122 completes a request, thereby preventingdouble spending or early usage of the transaction funds. Upon thefinancial institution computing system 104 receiving the completedtransaction descriptions, the account processing circuit 128 finalizesthe adjustment of the customer's financial account. Also, the accountprocessing circuit 128 stores all transaction information in an accountsdatabase 130 within the financial institution computing system 104. Forexample, the curbside implementation circuit 136, of the financialinstitution branch computing system 106, provides the account processingcircuit 128 with completed transaction descriptions at the completion ofa curbside transaction request. In some embodiments, either thefinancial institution branch computing system 106 or the financialinstitution computing system 104 keeps track of all the curbsidetransaction that are submitted and completed by a customer, in order tocomply with any regulatory rules. In other embodiments, both thefinancial institution and the financial institution branch computingsystem 104, 106 keep track of the transaction history, comprising thedetails from request submission to completion by the customer.

The financial account database 130 is structured to store accountinformation and transaction records for a plurality of customers of thefinancial institution. The account database 130 stores details regardingtypes of accounts held within a financial institution, the type ofaccount holder, whether he or she is authorized for the curbsidetransactions, information and video of each curbside transaction, and soon for a plurality of customers. A specific account in the accountsdatabase 130 may have a multi-use passcode, for example, a curbside fobor a biometric sample, that is used by the curbside management circuit122 to transmit the instructions to the financial institution branchcomputing system 106 to authenticate the customer. In particular, theaccount database 130 stores each transaction that occurred, and eachpayment includes the amount of the transaction, the transaction type,the transaction location, and the account source of the transaction.

The financial institution branch computing system 106 includes a networkinterface circuit 134 and a curbside implementation circuit 136. Thenetwork interface 134 is structured to facilitate operativecommunication between the financial institution branch computing system106 and other systems and devices via the network 108. The networkinterface 134 is also structured to facilitate operative communicationbetween the financial institution branch computing system 106 and thefinancial institution computing system 104 via the network 108. In somearrangements, the financial institution branch computing system 106 isconnected to the customer computing system 102 over the network 108, sothat the financial institution branch computing system 106 cancommunicate the finalized request transaction descriptions or anyupdates or changes to the customer. The financial institution branchcomputing system 106 may, for example, include one or more servers eachwith one or more processors configured to execute instructions stored ina memory, send and receive data stored in the memory, and perform otheroperations to implement the financial services described hereinassociated with the processing modules, databases, and processes shown.

The curbside implementation circuit 136 is structured to receive thefinalized transaction request from the financial institution computingsystem 104 and generate a plurality of commands to facilitate thecompletion of the curbside service transaction at the branch location.For example, one command could instruct a branch employee to physicallyprepare the relevant transaction materials in anticipation of thetransaction time. Another command could instruct an employee travel to anearby branch or institution to pick-up an amount of foreign currency.The curbside implementation circuit 136 includes a curbside detailcircuit 138, a customer detection circuit 140, and a curbside completioncircuit 142. The curbside implementation circuit 136 is in communicationwith the request circuit 124 of the financial institution computingsystem 104. As will be appreciated, the curbside implementation circuit136 can be in communication with or control a plurality of deliverymechanism (e.g., human worker at the branch, automated dispenser,autonomous device, drone, and the like) at the branch location.

The curbside detail circuit 138 is structured to track, maintain, andincorporate curbside transaction descriptions for an account enrolled inthe curbside transaction service with the financial institution. Thecurbside detail circuit 138 is structured to receive an instructiondetail message from the curbside instructions circuit 126 of thefinancial institution computing system 104. Upon receiving thetransaction instructions, the curbside detail circuit 138 ensures thatthe relevant curbside information is transmitted to the proper entities.For example, the curbside detail circuit 138 can cause a print out of atransaction request instruction on a computer screen of an employee atthe branch location. The employee would gather the materials (e.g.,currency, foreign currency, deposit slip, etc.) in accordance with theinstructions. For example, the employee could place an amount of U.S.D.into an envelope in accordance with the amount and denominationsspecified in the transaction request and store the envelope until thecustomer's transaction time window occurs. In some arrangements, thecurbside detail circuit 138 is operably connected to a processor thatcontrols a plurality of receptacles near the designated curbside pickuparea, wherein the contents of the transaction are delivered through anautomated service from inside the branch to the side of the vehicle. Insome embodiments, a combination of employee interaction and automatedactions is utilized to get the curbside ready for, and ultimatelydelivered to, the customer.

The customer detection circuit 140 is structured to notify the branchwhen the customer is approaching or has arrived at the branch locationto begin the requested transaction. In some embodiments, the customer“checks in” when arriving at the location, signaling to the branch toapproach the car and initiate the transition. This check in can be donethrough the curbside banking circuit 118 on the customer's mobilecomputing system 102. In some arrangements, the curbside banking circuit118 will, with the customer's permission, track the GPS of thecustomer's mobile computing device, thereby knowing the location of thecustomer as they approach, and eventually arrive, at the branchlocation. In some embodiments, the assigned parking spot at the branchlocation can automatically detect that the customer has arrived. Forexample, the spot may utilize a proximity sensor, a license platescanner, geo-fencing or a process that determines that the user's mobiledevice is within the designated parking spot.

In some arrangements a camera is connected to the customer detectioncircuit 140 and is used to view the parking spot. This can allow anemployee to ascertain an arrival event, the driver's identity and thevehicle information upon a vehicle arriving in the parking spot. Inother arrangements, the curbside location has an automated transportmechanism set up. For example, a system similar to the drive-thruoptions at financial institutions could be utilized, with a system oftubes connecting the financial institution branch to the variousreceptacles at the curbside pickup locations. Upon arrival, the branchcould authenticate the customer and quickly complete the transaction, asany currency would already prepared and ready to deliver to thecustomer.

The curbside completion circuit 142 is structured to complete thecustomer authentication for the transaction and generate a transactionconfirmation message that includes relevant transaction descriptions. Insome embodiments, the customer has to provide additional authenticationbefore gaining access to the items. The additional authentication couldbe, for example, a one-time passcode or barcode, presentment of ID(e.g., driver's license, passport, etc.), an account or multi-usepasscode or password, or a biometric sample that is presented to theemployee of the branch. In some arrangements, a branch employee has aphoto of the customer and/or the vehicle information of the pickupvehicle to use to authenticate the customer at the curbside pickuplocation. These identification items may be previously provided by thecustomer to the financial institution computing system. Upon receivingaccess to the transaction items the customer can complete thetransaction with the branch employee or curbside service receptacle. Insome arrangements, the customer has to provide a signature or swipe acard issued by the financial institution to finalize and approve thetransaction.

Upon completion of the transaction, the curbside completion circuit 142generates a transaction confirmation message and transmits it to thefinancial institution computing system 104. The transaction confirmationmessage includes relevant transaction descriptions, such as the type oftransaction that occurred, the amount of the transaction, the requestedtime window of the transaction, the actual time the transaction occurredand any additional notes on the transaction. In some embodiments, italso includes a video recording, from the cameras situated near theparking spot, of the transaction occurring. In some arrangements, thepicture of the customer could be captured and sent with the confirmationdetails.

Referring to FIG. 2, a flow diagram of a method 200 of transmitting acurbside transaction request is shown, according to an exampleembodiment. The method 200 is in connection with a customer's (e.g., anaccount holder at the financial institution) device, a financialinstitution, and a branch location of the financial institution. Forexample, the customer may be an individual who operates the customercomputing system 102 of FIG. 1. The financial institution may be afinancial institution that manages the financial institution computingsystem 104 of FIG. 1. The branch location may be an entity that managesthe financial institution branch computing system 106 of FIG. 1.However, the method 200 may be similarly performed by other systems anddevices.

The method 200 begins when a transaction request is transmitted from thecustomer to the financial institution at 202. The customer computingsystem 102 transmits the transaction request to the financialinstitution computing system 104 via the network 108. The transactionrequest includes various details defining the parameters of a requestedcurbside transaction from the customer associated with the customercomputing system 102. For example, the transaction request includes atransaction type (e.g., withdrawal, deposit, exchange, etc.), atransaction amount, a branch location, a time window, and a financialaccount to use to facilitate the transaction. The transaction type canbe a withdrawal, a deposit, a currency exchange or any other transactioninvolving the physical passing of items (e.g., coins and bills). Forexample, the customer could request an exchange, wherein the customerprovides 100 U.S.D. at the curbside service in exchange for theequivalent amount in Euros. In some arrangements, multiple transactiontypes could be requested in a single request. In some embodiments, thebranch location and time window can be determined in real-time as thecustomer enters in the transaction descriptions while creating therequest via the customer computing system 102. For example, as thecustomer enters a currency exchange request, the financial institutioncomputing system 104 can provide real-time feedback to the curbsidebanking circuit 118 of the customer computing system 102 indicatingavailable branch locations that could complete the transaction on theday of the request. As another example, the financial institution mayhave no branch available for any transaction for a given day,accordingly the financial institution computing system 104 can providereal-time feedback to the customer computing system 102 that causes thecurbside banking circuit 118 to only present available days in the timewindow field for the customer to schedule the transaction. In otherembodiments, the customer submits a desired branch location and timewindow to the financial institution, and receives an transaction requestapproval with the details, or a transaction request denial due tounavailability at the branch location at the specified time window.

At 204, the financial institution computing system 104 receives thetransaction request from the customer computing system 102 via thenetwork 108. After receiving the request, the financial institutioncomputing system 104 determines the feasibility of the transaction giventhe transaction parameters included in the transaction request. Forexample, the financial institution determines whether the requestedbranch location will be able to complete the withdrawal request betweenthe 3:15 PM and 3:20 PM, whether the customer's account has thenecessary funds, and the like.

At 206, the financial institution computing system 104 adjusts thecustomer's financial account by the transaction amount if the requestedtransaction requires an account adjustment. The transaction amountincludes the requested amount to be withdrawn, deposited or exchanged,and also includes fees associated with the transaction. Fees would beassociated with the financial institution and the use of the service. Insome embodiments, the account is tentatively adjusted, wherein themovement of the funds is shown in the account, but not yet finalized.For example, if the customer is withdrawing 100 U.S.D. from theiraccount which has 1,000 U.S.D., upon submission of the request, thecustomer may only be able to use 900 U.S.D. to initiate any subsequenttransaction with that account as a source despite not yet completing thewithdrawal. Similarly, if the customer is depositing 100 U.S.D. fromtheir account that has 1,000 U.S.D., upon submission of the request, thecustomer account balance may show 1,100 U.S.D. with only 1,000 U.S.D.available for immediate transactions. However, as noted above, not allrequested transaction types require an initial adjustment of thecustomer's account. For example, if the requested transaction relates toan exchange of bills for coins, no preliminary account balanceadjustment is needed.

At 208, the financial institution computing system 104 transmits aservice call to the financial institution branch computing system 106 toinitiate the transaction via the network 108. The service call is amessage transmitted from the financial institution computing system 104to the financial institution branch computing system 106 that instructsemployees of the branch to process and prepare the requestedtransaction. The service call includes several information fieldsregarding the transaction descriptions, the authentication details andthe location details. In one embodiment, the service call includesinstructions to an employee of the branch to ready an amount of acurrency to provide to the customer on arrival, for example in awithdrawal request or exchange request. In other embodiments, theservice call includes instructions to prepare for a collection of acertain amount of a currency from the customer on the customer'sarrival. The authentication details can include any identifyinginformation of the customer to authenticate his or her identity. In someembodiments, the customer has to provide a passcode, for example anaccount password or a transaction specific passcode generated by thefinancial institution. In other arrangements, the customer has toprovide a biometric sample. In some embodiments, the customer designatesa vehicle type and provides a photo of the customer to be used by theemployee at the branch location to authenticate the customer.

At 210, the financial institution computing system 104 transmits atransaction confirmation to the customer computing system 102 via thenetwork 108. The transaction confirmation includes details regarding thetransaction. For example, the transaction descriptions may include anyof a confirmation number associated with the transaction, a reminder asto which branch location the transaction can be completed at, a reminderas to the time window when the transaction can be completed, a reminderas to which parking space the customer is to park at, and the like. Insome arrangements, the details include a transaction specific passcodeor password for the customer to use to authenticate upon arrival at thebranch location. In other arrangements, the details include informationon how to change or cancel the submitted transaction request.

At 212, the transaction confirmation is received on the customercomputing system 102. Accordingly, the customer can view the transactionconfirmation and the associated transaction descriptions the next timehe or she logs into his or her account. In some arrangements, thecustomer computing system 102 presents the transaction confirmation uponreceipt as a push notification.

At 214, the financial institution branch computing system 106 receivesthe service call via the network 108. In some arrangements, the branchlocation may alter the transaction descriptions, and the financialinstitution branch computing system 106 can send the changes to thefinancial institution computing system 104 in response to the alteredtransaction, which in turn can send the update to the customer computingsystem 102. For example, if the branch location has an unexpected issuethat delays all the services, including the curbside service, thefinancial institution branch computing system 106 can initiate a messageto the customer computing system 102 via the financial institutioncomputing system 104 that informs the customer of the delay and a newpick-up time window. At 216, the financial institution branch computingsystem 106 generates and sends a message to an appropriate employee(e.g., via an employee computing device) instructing the transactioncompletion. In some arrangements, the message is an e-mail orin-application message transmitted to a specific employee identifier(e.g., an employee e-mail address). The message instructs the employeeto prepare the transaction items. For example, the message may instructthe employee to gather necessary funds (e.g., bills, coins, etc.) orprepare a deposit slip. In some arrangements, the branch location has toretrieve a non-U.S.D. currency from another location (e.g., anotherbranch location or a currency exchange partner) before the arrival ofthe customer.

Referring to FIG. 3, a flow diagram of a method 300 of completing acurbside transaction request is shown, according to an exampleembodiment. The method 300 may be performed in connection with themethod 200 of FIG. 2. However, the method 300 may similarly be performedin connection with other types of transactions. The method 300 is shownin connection with a customer's (e.g., an account holder at thefinancial institution) device, a branch location of the financialinstitution, and a financial institution. For example, the customer maybe an individual who operates the customer computing system 102 ofFIG. 1. The branch location may be an entity that manages the financialinstitution branch computing system 106 of FIG. 1. The financialinstitution may be a financial institution that manages the financialinstitution computing system 104 of FIG. 1. However, the method 300 maybe similarly performed by other systems and devices. As will beappreciated, the delivery mechanism for completing a curbsidetransaction request can include a human worker at the branch, anautomated dispenser, an autonomous device, a drone, or similar deliverymechanisms.

The method 300 begins when a transaction request confirmation isreceived by the customer from the financial institution at 302. Thefinancial institution computing system 104 transmits the transactionrequest confirmation details to the customer computing system 102 viathe network 108. The transaction confirmation includes details regardingthe transaction. For example, the transaction descriptions may includeany of a confirmation number associated with the transaction, a reminderas to which branch location the transaction can be completed at, areminder as to the time window when the transaction can be completed, areminder as to which parking space the customer is to park at, and thelike. In some arrangements, the details include a transaction specificpasscode or password for the customer to use to authenticate uponarrival at the branch location. In other arrangements, the detailsinclude information on how to change or cancel the submitted transactionrequest. For example, the customer receives a branch location streetaddress and a designated parking spot to park in, a password of“password 123” which is needed to complete the withdrawal request, and atime window of 1:15 PM and 1:20 PM.

At 304, an arrival notification is transmitted. The customer arrives atthe branch location around the time range specified in the transactionrequest confirmation details. An arrival notification is transmitted tothe financial institution branch computing system 106. In somearrangements, the customer computing system 102 (e.g., mobile device)transmits the arrival notification to the financial institution branchcomputing system 106 via the network 108. For example, the customer“checks in” on his or her mobile device when they arrive at thelocation, signaling to the branch to approach the customer's car andinitiate the transition. The check in may be done through an applicationwith the financial institution on the customer's mobile computing device102. In some arrangements, the financial institution's application will,with customer permission, track the GPS of the customer's mobilecomputing device, thereby knowing the location of the customer as theyapproach, and eventually arrive, at the branch location. In furtherarrangements, the financial institution branch computing system 106automatically detects the arrival of the customer (e.g., via a licenseplate scanner, via geofencing, via a received biometric of the customer,etc.).

Upon arrival by the customer, at 306, the financial institution branchcomputing system 106 receives the customer arrival notification. In someembodiments, the arrival notification is generated within the financialinstitution branch computing system 106. For example, the designatedparking spot at the branch location can automatically detect that avehicle arrived in the spot. In some arrangements, the parking spotutilizes a proximity sensor, a license plate scanner, geo-fencing or bypinging that the customer's mobile device when the device is within arange of the designated parking spot. In other arrangements, a cameracould be positioned to view the parking spot and an employee initiatesthe arrival notification when the employee views the customer designatedvehicle type and provided photo of the customer.

At 308, the financial institution branch computing system 106facilitates the transport of the transaction items to the vehicle in theparking lot. The financial institution branch computing system 106generates and sends a message to an appropriate employee (e.g., via anemployee computing device) instructing the employee to transport thetransaction items to a parking spot. For example, an employee receives anotification on a computing device informing them to take the U.S.D.currency in curbside preparation slot one to parking spot A within inthe next five minutes.

At 310, the customer computing system 102 accesses the transaction itemstransported to the customer vehicle. The customer computing system 102may receive a notification from the financial institution branchcomputing system 106 indicating that a branch employee is bringing thetransaction items to the customer's vehicle. In some embodiments, thecustomer has to provide additional authentication to the branch employeebefore gaining access to the items. The additional authentication couldbe, for example, a one-time passcode or barcode, presentment of ID, anaccount or multi-use passcode or password, or a biometric sample to theemployee. At 312, the customer computing system 102 transmits acompleted transaction notification to the financial institution branchcomputing system 106. For example, the customer confirms that thetransaction items were received on the customer's mobile device. In somearrangements, the customer has to provide a signature to the employee orswipe a card issued by the financial institution on an branch employeecomputing system to finalize and approve the transaction.

At 314, the financial institution branch computing system 106 receivesthe completed transaction notification via the network 108. In somearrangements, the completed transaction notification is transmitted fromthe customer computing system 102. In other arrangements, the completedtransaction notification is transmitting from a computing device of thebranch employee. For example, the employee has the customer sign on anemployee computing device once the transaction is finished. Thecompleted transaction notification includes several information fieldsregarding the transaction completion. In one embodiment, the completedtransaction notification includes the name of the branch employee whofacilitated the transaction with the customer. In other embodiments, thecompleted transaction notification includes the arrival time of thecustomer and the time that the completion was finalized. In someembodiments, the completed transaction notification includes informationregarding issues or problems that arose during the transaction. Forexample, the transaction items were improperly prepared and there was adeficiency in the U.S.D. transported to the customer.

At 316, the financial institution branch computing system 106 transmitsa transaction confirmation to the financial institution computing system104 via the network 108. The transaction confirmation includes severalinformation fields regarding the transaction as requested and eventuallycompleted. In one embodiment, the transaction confirmation includes thetype of transaction that was requested, the amount of the transaction,the time window of the transaction, the actual time the transactionoccurred and the amount of currency provided to the customer. In someembodiments, the transaction confirmation includes a video, from thecameras situated near the parking spot, of the transaction occurring. Insome arrangements, the transaction confirmation includes the detailsprovided in the completed transaction notification.

At 318, the financial institution computing system 104 receives thetransaction confirmation from the financial institution branch computingsystem 106 via the network 108. The financial institution computingsystem 104 determines whether or not the transaction was completedcorrectly, in accordance with the request. If the transaction completeddetails show a shortcoming by the branch, the financial institution maytry to rectify those issues moving forward in order to improve thecustomer experience with the service.

At 320, the financial institution computing system 104 finalizes theadjustment of the customer's financial account by the transactionamount. In some embodiments, the account has been previously tentativelyadjusted, wherein the movement of the funds is shown in the account, butnot yet finalized, for example, at 208 of the method 200 of FIG. 2. Inother embodiments, the account is only adjusted by the transactionamount upon completion of the transaction. The transaction amountincludes the actual amount that was withdrawn, deposited or exchanged,and also includes fees associated with the transaction. Fees would beassociated with the financial institution and the use of the service.Not all requested transaction types require a finalized adjustment ofthe customer's account. For example, if the requested transactionrelates to an exchange of bills for coins, no account balance adjustmentis needed.

At 322, the financial institution computing system 104 transmits acurbside confirmation message to the customer computing system 102 viathe network 108. The curbside confirmation message includes detailsregarding the requested and completed curbside transaction. For example,the curbside confirmation details may include any of a confirmationnumber associated with the transaction, a summary of the requestedtransaction, a summary of the transaction as completed, an accountupdate reflected the transaction, and the like. At 324, the curbsideconfirmation is received on the customer computing system 102.Accordingly, the customer can view the curbside confirmation and theassociated transaction descriptions the next time he or she logs intohis or her account. In some arrangements, the customer computing system102 presents the curbside confirmation upon receipt as a pushnotification.

FIGS. 4A-4D illustrate an example graphical user interface (“GUI”) 400that may be utilized to submit a curbside transaction request, accordingto an example embodiment. For example, the GUI 400 is displayed to thecustomer via the customer computing system 102 of FIG. 1. The GUI 400may be utilized in connection with the method 200 of FIG. 2 and themethod 300 of FIG. 3, according to example embodiments. For example, thecustomer utilizes the GUI 400 to submit a curbside transaction request,via method 200. As another example, the customer utilizes the GUI 400 toreceive a curbside transaction request confirmation from the financialinstitution and complete the curbside transaction, via method 300.However, it should be understood that the GUI 400 may similarly beutilized on other devices to conduct curbside transactions.

FIG. 4A illustrates a menu page 401 of the GUI 400, according to anembodiment. The GUI 400 includes a mobile banking interface that isdisplayed to the customer after accessing the curbside banking circuit118 that has been installed on the customer computer system 102. Inanother embodiment, the GUI 400 may similarly be accessed via an onlinebanking website. Upon accessing the GUI 400, the customer is prompted toprovide login credentials to gain access to the account with thefinancial institution. By providing such credentials, the customer isprovided with the full functionality of the online banking system in thecurbside banking circuit. In an example embodiment, the menu page 401includes a plurality of menu option for the customer's specificfinancial account 402. In this example, the customer is authorized toexecute curbside services from the customer's financial account. Themenu page 401 includes several menu buttons labeled with a correspondingaction. For example, the menu buttons include a withdraw button 404, adeposit button 406, an exchange button 408, and a transaction history410 button.

Referring now to FIG. 4B, a curbside service withdraw funds page 412 ofthe GUI 400 of FIG. 4A is illustrated. For example, the curbside servicewithdraw funds page 412 is displayed in response to a customer selectionof the withdraw button 404 on the menu bar provided in FIG. 4A. Thecurbside service withdraw funds page 412 provides the customer aplurality of fields to easily facilitate receiving cash, curbside at abranch location. According to an embodiment, the curbside servicewithdraw funds page 412 includes a source account field 414, a sourceaccount balance field 416, an amount field 418, a zip code field 420, abranch location field 422, a pickup passcode field 424, a pickup datefield 426, and a pickup time field 428. The source account field 414defines which account the customer would like to use to complete thetransaction. This could be, for example, the checking account for whichthe customer would like the withdrawn funds to be taken from. In somearrangements, the source account field 414 is defaulted to the accountthat was originally selected to begin the curbside service transactionservice, for example the specific financial account 402 as shown in FIG.4A. The customer may change the source account fund to another financialaccount with the financial institution, that causes the specificfinancial account 402 to update to the newly selected option.

The source account balance field 416 displays the amount of availablefunds in the selected account in the source account field 414. Thesource account balance field 416 will update, in real-time, the balancedepending on the account selected by the customer. The amount field 418displays how much the customer would like to use in the selectedcurbside transaction. For example, the customer selects to withdraw fromthe selected account 10 U.S.D. In some arrangements, the amount field418 will only allow the customer to enter an amount less than or equalto the source account balance field 416. In some arrangements, when thecustomer selects the withdraw option and enters the amount of currencyto be withdrawn, the customer may get an additional field that allowsthe customer to enter the denominations of each value of currency he orshe would like. For example, if the customer requests to withdraw 30U.S.D. from the checking account, an additional field may allow thecustomer to designate that he or she receives one ten dollar bill andone twenty dollar bill.

The zip code field 420 allows the customer to enter the zip code for thearea in which he or she would like to find a financial institutionbranch location to complete the transaction. In some arrangements, thecustomer is able to enter a full address in the zip code field 420 toprovide for more accurate location matching by the financialinstitution. The branch location field 422 is a drop down menu of allthe branch locations within the customer entered zip code. In somearrangements, the branch location field 422 is updated in real-time, inresponse to the value entered in the zip code field 422. In otherarrangements, the branch location field 422 updates in response to thecustomer entering in a desired pickup date and pickup time in theirfields, respectively 426 and 428.

The pickup passcode field 424 allows the customer to choose which formof authentication is to be used by the branch location on the subsequentcurbside transaction by the customer. As shown in FIG. 4B, the customermay require that the financial institution email a one-time passcode tothe customer's email address, that the customer provide a biometricsample, that the customer provide a multi-use account password, or thatthe customer be able to utilize near field communication toauthenticate. In other arrangements, the customer has a curbside servicetransaction profile with possible vehicle identification informationand/or a customer photograph.

The pickup date field 426 allows the customer to enter the date that thecustomer would like to complete the curbside transaction. In somearrangements, the branch location field 422 updates, in real-time, inresponse to the pickup date options displayed in the field 426. In someembodiments, the pickup date field 426 is a drop down option menu, theoptions responsive to the transaction type and selected branch location.In other arrangements, the customer enters in a the date, in someformat, for example MM/DD/YYYY.

The pickup time field 428 allows the customer to select the time windowfor which they would like to complete the curbside transaction. In somearrangements, the pickup time field is a drop down selection responsiveto the transaction type, transaction location and transaction dateentries. The drop down selection could specify a single time entry forwhich the transaction is requested to be ready by, as shown in FIG. 4B,or may be a selection of a range of time, for example from 11:30 AM to11:45 AM. In other arrangements, the pickup time field 428 is an emptyfield that the customer enters any valid time into. In somearrangements, the customer entering a pickup time and pickup datecombination first, changes the available branch locations, as somelocations may be unable to handle the transaction type and the requesteddate and time. The customer chooses to approve the transaction displayedby selecting the “Submit” button 432, or the customer may cancel thetransaction request via the “Cancel” button 430 In some embodiments,either selection leads to an additional confirmation prompt by theapplication.

Referring now to FIG. 4C, a curbside service withdraw funds requestsummary page 438 of the GUI 400 of FIG. 4A is illustrated. For example,withdraw funds request summary page 438 is displayed in response to acustomer selection of the “Submit” button 432 on the button bar providedin FIG. 4B. The withdraw funds request summary page 438 provides thecustomer a plurality of fields that summarize the details regarding therequest submission, and reflects availability changes. According to anembodiment, the withdraw funds request summary page 438 includes asource account field 440, a transaction amount field 442, a fees field444, a source account balance field 446, and a location details field448.

The source account field 440, the transaction amount field 442 and thesource account balance field 446 display the information entered intothe withdraw funds page 412 as shown in FIG. 4B. The fees field 444 ofthe GUI 400 displays fees associated with the transaction. The totaltransaction amount includes the requested amount to be transmitted tothe recipient, and any fees associated with the transaction.

The location details field 448 includes the relevant information for thecustomer to arrive at the proper branch location and complete thetransaction. The location details field includes a plurality of fieldsthat summarize the location details and include a branch location field450, a passcode field 452, a pickup vehicle field 454, a pickup datefield 456, a pickup time field 458 and a customer photo 460. The branchlocation field 450 is the customer selected option from the drop downmenu of all the branch locations within the customer entered zip code.The passcode field 452 displays the customer's selection for the form ofauthentication to be used by the branch location on the curbsidetransaction. For example, the customer may have requested that thefinancial institution email a one-time password to the customer's emailaddress, such as “jDoe@email.com” as shown in FIG. 4C.

The pickup vehicle field 454 displays the customer's informationregarding the information of the vehicle that will be used to completethe curbside transaction. In some arrangements, the vehicle informationmay include the vehicle model, vehicle manufacturer, vehicle year,vehicle color, and license plate number of the vehicle. In somearrangements, a customer has multiple vehicles on a curbside profiletied to the financial institution account. In other arrangements, apicture of the vehicle is uploaded onto the customer's curbside profile.

The pickup data field 456 displays the customer's choice of the datethat the customer would like to complete the curbside transaction. Insome arrangements, the date is a result of the financial institutionchoosing the best date based on a multiple date options selected by thecustomer in a previous menu. The pickup time field 458 displays the timewindow for which the customer would like to complete the curbsidetransaction. The customer photo 460 can be a photo of the customer thatwill be completing the transaction and the photo can be transmitted toan employee of the branch and used to provide additional authenticationto complete the transaction.

The withdraw funds request summary page 438 of the GUI 400 also includesa “change date and/or time” button 462 that allows the customer to alterthe location and timing details of the curbside transaction. Thecustomer chooses to approve the transaction displayed by selecting the“Confirm” button 466, or the customer may cancel the transaction requestvia the “Cancel” button 464. In some embodiments, either selection leadsto an additional confirmation prompt by the application.

Referring now to FIG. 4D, a curbside service exchange funds page 470 ofthe GUI 400 of FIG. 4A is illustrated. For example, the curbside serviceexchange funds page 470 is displayed in response to a customer selectionof the exchange button 408 on the menu bar provided in FIG. 4A. Thecurbside service exchange funds page 470 provides the customer aplurality of fields to easily facilitate receiving cash, curbside at abranch location. According to an embodiment, the curbside serviceexchange funds page 470 includes a source account field 472, a sourceaccount balance field 474, an exchange amount field 476, an equivalentamount field 478, a zip code field 480, a branch location field 482, apickup date field 484, and a pickup time field 486. In somearrangements, the GUI 400 displays a pickup passcode field that allowsthe customer to choose which form of authentication to be used by thebranch location on the subsequent curbside transaction by the customer.

The source account field 472 defines which account the customer wouldlike to use to complete the transaction. This could be, for example, thechecking account for which the customer would like the withdrawn fundsto be taken from. In some arrangements, the source account field 472 isdefaulted to the account that was originally selected to begin thecurbside service transactions, for example the specific financialaccount 402 as shown in FIG. 4A. The customer may change the sourceaccount fund to another financial account with the financialinstitution, that causes the specific financial account 402 to update tothe newly selected option. In some arrangements, the customer selects topay for the exchange upon arrival at the branch location. For example,the customer could provide 100 U.S.D. in cash at the curbside locationto the employee in exchange for the equivalent amount.

The source account balance field 474 displays the amount of availablefunds in the selected account in the source account field 472. Thesource account balance field 474 will update, in real-time, the balancedepending on the account selected by the customer. The amount field 474displays how much the customer would like to use in the exchangecurrency curbside transaction. For example, the customer selects towithdraw from the selected account 100 U.S.D. In some arrangements, theamount field 476 only allows for the customer to enter an amount lessthan or equal to the source account balance field 474. In somearrangements, when the customer selects the exchange option and entersthe amount of currency to be exchanged, the customer gets an additionalfield that allows the customer to enter the denominations of each valueof currency he or she would like to end up with at the completion of theexchange. For example, if the customer requests to withdraw 30 U.S.D.from the checking account for the equivalent amount of a foreigncurrency, for example Euros, an additional field allows for the customerto designate that he or she receives fourteen €2 coins. In somearrangements, the customer selects to receive an amount of the foreigncurrency. For example, the customer could request 100 Euros and theequivalent amount field 478 would display the equivalent amount ofU.S.D. that would be required to complete the transaction.

The equivalent amount field 478 of the GUI 400 displays an amount in thecustomer's primary fiat currency (e.g., U.S.D.) that is equivalent tothe amount of foreign currency requested in the exchange amount field476. For example, as shown in FIG. 4D, if the U.S.D. amount in theamount field 476 is 100 U.S.D., the equivalent amount field 478 of theGUI 400 displays the amount of euro currency equivalent to the requestedamount of U.S.D. In some arrangements where the customer selects toreceive an amount of the foreign currency, the equivalent amount field478 displays how much U.S.D. currency is required to complete theexchange. For example, the customer could request 100 Euros and theequivalent amount field 478 would display the equivalent amount ofU.S.D. that would be required to complete the transaction, 120 U.S.D.

The zip code field 480 allows the customer to enter the zip code for thearea in which he or she would like to find a financial institutionbranch location to complete the transaction. In some arrangements, thecustomer is able to enter a full address in the zip code field 480 toprovide for more accurate location matching by the financialinstitution. The branch location field 482 is a drop down menu of allthe branch locations within the customer entered zip code. In somearrangements, the branch location field 482 is updated in real-time, inresponse to the value entered in the zip code field 480. In somearrangements, the branch location field 482 may be limited due to branchlocations lacking the currency type that the customer wants to exchangethe U.S.D. for. In other arrangements, the branch location field 482updates in response to the customer entering in a desired pickup dateand pickup time in their fields, respectively 484 and 486.

The pickup date field 484 allows the customer to enter the date that thecustomer would like to complete the curbside transaction. In somearrangements, the branch location field 484 updates, in real-time, thepickup date options displayed in the field 484. In some embodiments, thepickup date field 484 is a drop down option menu, the options responsiveto the transaction type and selected branch location. In otherarrangements, the customer enters in a the date, in some format, forexample MM/DD/YYYY.

The pickup time field 486 allows the customer to select the time windowfor which they would like to complete the curbside transaction. In somearrangements, the pickup time field 486 is a drop down selectionresponsive to the transaction type, transaction location and transactiondate entries. The drop down selection could specify a single time entryfor which the transaction is requested to be ready by, as shown in FIG.4D, or a selection of a range of time, for example from 11:30 AM to11:45 AM. In other arrangements, the pickup time field 486 is an emptyfield that the customer enters any valid time into. In somearrangements, the customer entering a pickup time and pickup datecombination first, may change the available branch locations, as somelocations may be unable to handle the transaction type and the requesteddate and time. The customer chooses to approve the transaction displayedby selecting the “Submit” button 490, or the customer may cancel thetransaction request via the “Cancel” button 488. In some embodiments,either selection leads to an additional confirmation prompt by theapplication.

The embodiments described herein have been described with reference todrawings. The drawings illustrate certain details of specificembodiments that implement the systems, methods and programs describedherein. However, describing the embodiments with drawings should not beconstrued as imposing on the disclosure any limitations that may bepresent in the drawings.

It should be understood that no claim element herein is to be construedunder the provisions of 35 U.S.C. § 112(f), unless the element isexpressly recited using the phrase “means for.”

As used herein, the term “circuit” may include hardware structured toexecute the functions described herein. In some embodiments, eachrespective “circuit” may include machine-readable media for configuringthe hardware to execute the functions described herein. The circuit maybe embodied as one or more circuitry components including, but notlimited to, processing circuitry, network interfaces, peripheraldevices, input devices, output devices, sensors, etc. In someembodiments, a circuit may take the form of one or more analog circuits,electronic circuits (e.g., integrated circuits (IC), discrete circuits,system on a chip (SOCs) circuits, etc.), telecommunication circuits,hybrid circuits, and any other type of “circuit.” In this regard, the“circuit” may include any type of component for accomplishing orfacilitating achievement of the operations described herein. Forexample, a circuit as described herein may include one or moretransistors, logic gates (e.g., NAND, AND, NOR, OR, XOR, NOT, XNOR,etc.), resistors, multiplexers, registers, capacitors, inductors,diodes, wiring, and so on).

The “circuit” may also include one or more processors communicativelycoupled to one or more memory or memory devices. In this regard, the oneor more processors may execute instructions stored in the memory or mayexecute instructions otherwise accessible to the one or more processors.In some embodiments, the one or more processors may be embodied invarious ways. The one or more processors may be constructed in a mannersufficient to perform at least the operations described herein. In someembodiments, the one or more processors may be shared by multiplecircuits (e.g., circuit A and circuit B may comprise or otherwise sharethe same processor which, in some example embodiments, may executeinstructions stored, or otherwise accessed, via different areas ofmemory). Alternatively or additionally, the one or more processors maybe structured to perform or otherwise execute certain operationsindependent of one or more co-processors. In other example embodiments,two or more processors may be coupled via a bus to enable independent,parallel, pipelined, or multi-threaded instruction execution. Eachprocessor may be implemented as one or more general-purpose processors,application specific integrated circuits (ASICs), field programmablegate arrays (FPGAs), digital signal processors (DSPs), or other suitableelectronic data processing components structured to execute instructionsprovided by memory. The one or more processors may take the form of asingle core processor, multi-core processor (e.g., a dual coreprocessor, triple core processor, quad core processor, etc.),microprocessor, etc. In some embodiments, the one or more processors maybe external to the apparatus, for example the one or more processors maybe a remote processor (e.g., a cloud based processor). Alternatively oradditionally, the one or more processors may be internal and/or local tothe apparatus. In this regard, a given circuit or components thereof maybe disposed locally (e.g., as part of a local server, a local computingsystem, etc.) or remotely (e.g., as part of a remote server such as acloud based server). To that end, a “circuit” as described herein mayinclude components that are distributed across one or more locations.

An example system for implementing the overall system or portions of theembodiments might include a general purpose computing computers in theform of computers, including a processing unit, a system memory, and asystem bus that couples various system components including the systemmemory to the processing unit. Each memory device may includenon-transient volatile storage media, non-volatile storage media,non-transitory storage media (e.g., one or more volatile and/ornon-volatile memories), etc. In some embodiments, the non-volatile mediamay take the form of ROM, flash memory (e.g., flash memory such as NAND,3D NAND, NOR, 3D NOR, etc.), EEPROM, MRAM, magnetic storage, hard discs,optical discs, etc. In other embodiments, the volatile storage media maytake the form of RAM, TRAM, ZRAM, etc. Combinations of the above arealso included within the scope of machine-readable media. In thisregard, machine-executable instructions comprise, for example,instructions and data which cause a general purpose computer, specialpurpose computer, or special purpose processing machines to perform acertain function or group of functions. Each respective memory devicemay be operable to maintain or otherwise store information relating tothe operations performed by one or more associated circuits, includingprocessor instructions and related data (e.g., database components,object code components, script components, etc.), in accordance with theexample embodiments described herein.

It should also be noted that the term “input devices,” as describedherein, may include any type of input device including, but not limitedto, a keyboard, a keypad, a mouse, joystick or other input devicesperforming a similar function. Comparatively, the term “output device,”as described herein, may include any type of output device including,but not limited to, a computer monitor, printer, facsimile machine, orother output devices performing a similar function.

Any foregoing references to currency or funds are intended to includefiat currencies, non-fiat currencies (e.g., precious metals), andmath-based currencies (often referred to as cryptocurrencies). Examplesof math-based currencies include Bitcoin, Litecoin, Dogecoin, and thelike.

It should be noted that although the diagrams herein may show a specificorder and composition of method steps, it is understood that the orderof these steps may differ from what is depicted. For example, two ormore steps may be performed concurrently or with partial concurrence.Also, some method steps that are performed as discrete steps may becombined, steps being performed as a combined step may be separated intodiscrete steps, the sequence of certain processes may be reversed orotherwise varied, and the nature or number of discrete processes may bealtered or varied. The order or sequence of any element or apparatus maybe varied or substituted according to alternative embodiments.Accordingly, all such modifications are intended to be included withinthe scope of the present disclosure as defined in the appended claims.Such variations will depend on the machine-readable media and hardwaresystems chosen and on designer choice. It is understood that all suchvariations are within the scope of the disclosure. Likewise, softwareand web implementations of the present disclosure could be accomplishedwith standard programming techniques with rule based logic and otherlogic to accomplish the various database searching steps, correlationsteps, comparison steps and decision steps.

The foregoing description of embodiments has been presented for purposesof illustration and description. It is not intended to be exhaustive orto limit the disclosure to the precise form disclosed, and modificationsand variations are possible in light of the above teachings or may beacquired from this disclosure. The embodiments were chosen and describedin order to explain the principals of the disclosure and its practicalapplication to enable one skilled in the art to utilize the variousembodiments and with various modifications as are suited to theparticular use contemplated. Other substitutions, modifications, changesand omissions may be made in the design, operating conditions andarrangement of the embodiments without departing from the scope of thepresent disclosure as expressed in the appended claims.

What is claimed:
 1. A method for completing a curbside transaction, themethod comprising: receiving, by a financial institution computingsystem of a financial institution, a curbside transaction descriptionfrom a user device, the user device associated with an account holder ofthe financial institution, and the curbside transaction descriptioncomprising at least one of a transaction time, a branch location, and atransaction to be completed at the branch location, the branch locationassociated with a branch of the financial institution; transmitting, bythe financial institution computing system, a curbside set-up request toa branch location computing system associated with the branch location,the curbside set-up request comprising the curbside transactiondescription; transmitting, by the financial institution computingsystem, curbside transaction information to the user device, thecurbside transaction information comprising a location request, thelocation request associated with the user device providing locationinformation of the user device; receiving, by the financial institutioncomputing system, location information from the user device indicativeof the user device being located at the branch location; receiving, bythe financial institution computing system, an authentication identifierfrom the user device, the authentication identifier previously stored onthe user device, wherein receiving the authentication identifierinitiates the curbside transaction; and servicing the account holder viaa receptacle of a plurality of receptacles, the receptacle chosen basedon the location information and the curbside transaction description. 2.The method of claim 1, wherein the curbside transaction description is afunds withdrawal and the curbside transaction description furthercomprises an amount of a currency type, further comprising transmitting,by the financial institution computing system, a funds withdrawalmessage to the branch location computing system, the funds withdrawalmessage comprising instructions to an employee at the branch location toprepare the amount of the currency type.
 3. The method of claim 1,wherein the curbside transaction description is a funds withdrawal andthe curbside transaction description further comprises an amount of acurrency type, further comprising dispensing, to the account holderassociated with the user device, the amount of the currency type.
 4. Themethod of claim 1, wherein the curbside transaction description is afunds deposit, further comprising: transmitting, by the financialinstitution computing system, a funds deposit message to the branchlocation computing system, the funds deposit message comprisinginstructions to an employee at the branch location to prepare areceptacle to receive currency.
 5. The method of claim 1, furthercomprising, transmitting, by the financial institution computing system,a ready transaction notification to the user device, the readytransaction notification indicating that a pending transactionassociated with the curbside transaction information is ready to becompleted by the account holder at the branch location.
 6. The method ofclaim 1, wherein the authentication identifier relates to at least oneof a password string, fob, a scan of a biometric sample of the accountholder, or a request to present identification.
 7. The method of claim1, wherein the authentication identifier is transmitted via near-fieldcommunication (NFC) from the user device to a reader device associatedwith the financial institution computing system.
 8. A non-transitorycomputer readable media having computer-executable instructions embodiedtherein that, when executed by a computing system associated with afinancial institution causes the financial institution computing systemto perform operations for completing a curbside transaction, theoperations comprising: receiving a curbside transaction description froma user device, the user device associated with an account holder of thefinancial institution, and the curbside transaction descriptioncomprising at least one of a transaction time, a branch location, and atransaction to be completed at the branch location, the branch locationassociated with a branch of the financial institution; transmitting acurbside set-up request to a branch location computing system associatedwith the branch location, the curbside set-up request comprising thecurbside transaction description; transmitting curbside transactioninformation to the user device, the curbside transaction informationcomprising a location request, the location request associated with theuser device providing location information of the user device; receivinglocation information from the user device indicative of the user devicebeing located at the branch location; receiving an authenticationidentifier from the user device, the authentication identifierpreviously stored on the user device, wherein receiving theauthentication identifier initiates the curbside transaction; andservicing the account holder via a receptacle of a plurality ofreceptacles, the receptacle chosen based on the location information andthe curbside transaction description.
 9. The computer readable media ofclaim 8, wherein the curbside transaction description is a fundswithdrawal and the curbside transaction description further comprises anamount of a currency type, further comprising, transmitting a fundswithdrawal message to the branch location computing system, the fundswithdrawal message comprising instructions to an employee at the branchlocation to prepare the amount of the currency type.
 10. The computerreadable media of claim 8, wherein the curbside transaction descriptionis a funds withdrawal and the curbside transaction description furthercomprises an amount of a currency type, further comprising, dispensing,to the account holder associated with the user device, the amount of thecurrency type.
 11. The computer readable media of claim 8, wherein thecurbside transaction description is a funds deposit, the operationsfurther comprising: transmitting a funds deposit message to the branchlocation computing system, the funds deposit message comprisinginstructions to an employee at the branch location to prepare areceptacle to receive currency.
 12. The computer readable media of claim8, wherein the authentication identifier relates to at least one of apassword string, fob, a scan of a biometric sample of the accountholder, or a request to present identification.
 13. The computerreadable media of claim 8, wherein the authentication identifier istransmitted via near-field communication (NFC) from the user device to areader device associated with the financial institution computingsystem.
 14. A financial institution computing system associated with afinancial institution, the computing system comprising: a networkinterface configured to communicate data regarding a curbsidetransaction to and from a branch location computing system associatedwith a branch of the financial institution and a user device associatedwith a user over a network; and a circuit configured to: receive acurbside transaction description from the user device, the user deviceassociated with an account holder of the financial institution, and thecurbside transaction description comprising at least one of atransaction time, a branch location, and a transaction to be completedat the branch location, the branch location associated with the branchof the financial institution; transmit a curbside set-up request to thebranch location computing system associated with the branch location,the curbside set-up request comprising the curbside transactiondescription; transmit curbside transaction information to the userdevice, the curbside transaction information comprising a locationrequest, the location request associated with the user device providinglocation information of the user device; receive location informationfrom the user device indicative of the user device being located at thebranch location; receive an authentication identifier from the userdevice, the authentication identifier previously stored on the userdevice, wherein receiving the authentication identifier initiates thecurbside transaction; and service the account holder via a receptaclechosen based on the location information and the curbside transactiondescription.
 15. The financial institution computing system of claim 14,wherein the curbside transaction description is a funds withdrawal andthe curbside transaction description further comprises an amount of acurrency type, and wherein the circuit is further structured to transmita funds withdrawal message to the branch location, the funds withdrawalmessage comprising instructions to an employee at the branch to preparethe amount of the currency type.
 16. The financial institution computingsystem of claim 14, wherein the curbside transaction description is awithdrawal and the curbside transaction description further comprises anamount of a currency type, further comprising, dispensing, to theaccount holder associated with the user device, the amount of thecurrency type.
 17. The financial institution computing system of claim14, wherein the curbside transaction description is a currency exchange,and wherein the curbside transaction description comprises a firstamount of a first currency type and a second amount of a second currencytype, the second amount of the second currency type being what theaccount holder must provide to acquire the first amount of the firstcurrency type.
 18. The financial institution computing system of claim14, wherein the circuit is further structured to transmit a readytransaction notification to the user device, the ready transactionnotification indicating that a pending transaction associated with thecurbside transaction information is ready to be completed by the accountholder at the branch location.
 19. The financial institution computingsystem of claim 14, wherein the authentication identifier comprises apass code authentication, the pass code authentication being at leastone of a password string, fob, biometric scan, or a request to presentidentification.
 20. The financial institution computing system of claim14, wherein the authentication identifier is transmitted via near-fieldcommunication (NFC) from the user device associated with the financialinstitution computing system.